chore: Add Arc chain#204
Conversation
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 8e854bced6
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| oftEid: PRODUCTION_OFT_EIDs.ARBITRUM, | ||
| hypDomainId: MAINNET_CHAIN_IDs.ARBITRUM, | ||
| }, | ||
| [CHAIN_IDs.ARC]: { |
There was a problem hiding this comment.
This adds Arc to PRODUCTION_NETWORKS, so production consumers that enumerate supported chains or use the fallback RPC/explorer will treat chain 5042 as live. Arc's public docs currently identify the public testnet as the active network with chain ID 5042002 and say mainnet endpoints/parameters are published separately when available; Circle's domain 26 is also listed for Arc Testnet. Until real mainnet parameters exist, this should stay only in TEST_NETWORKS to avoid routing production flows to placeholder/non-live Arc endpoints.
Useful? React with 👍 / 👎.
2 participants
No description provided.